fix: bump PluginKit version to 3 to reject stale registry plugins#444
Merged
fix: bump PluginKit version to 3 to reject stale registry plugins#444
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
currentPluginKitVersionfrom 2 to 3 inPluginManager.swiftTableProPluginKitVersionfrom 2 to 3 in all 19 pluginInfo.plistfilesContext
Fixes #443. Users with stale registry-installed plugins (e.g., MongoDBDriver compiled against PluginKit v2) crash on launch with
EXC_BAD_INSTRUCTIONbecause theDriverPluginprotocol ABI changed but the version was never bumped. The existing version guard now correctly rejects these stale plugins at discovery time instead of loading them and crashing.Test plan
~/Library/Application Support/TablePro/Plugins/— should skip it with a log warning instead of crashing